Content Library Item Storage Info
The Content Library Item Storage Info schema is the expanded form of Content Library Item File Info that includes details about the storage backing for a file in a library item.
{
"storage_backing": {
"type": "string",
"datastore_id": "string",
"storage_uri": "string"
},
"storage_uris": [
"string"
],
"checksum_info": {
"algorithm": "string",
"checksum": "string"
},
"name": "string",
"size": 0,
"cached": false,
"version": "string",
"file_download_endpoint": "string"
}
The storage backing on which this object resides. This might not be the same as the default storage backing associated with the library.
URIs that identify the file on the storage backing.
These URIs may be specific to the backing and may need interpretation by the client. A client that understands a URI scheme in this list may use that URI to directly access the file on the storage backing. This can provide high-performance support for file manipulation.
A checksum for validating the content of the file.
This value can be used to verify that a transfer was completed without errors.
A checksum cannot always be calculated, and the value will be missing or null
if the file does not have content.
The name of the file.
This value will be unique within the library item for each file. It cannot be an empty string.
The file size, in bytes. The file size is the storage used and not the uploaded or provisioned size. For example, when uploading a disk to a datastore, the amount of storage that the disk consumes may be different from the disk file size. When the file is not cached, the size is 0.
Indicates whether the file is on disk or not.
The version of this file; incremented when a new copy of the file is uploaded.
The URL endpoint that can be used to download the file.
Eg URL: https://{vc}/cls/static/{libraryId}/{itemId}/{fileName}?version={version} Content Library Item File Info.version query param in the URL specifies the latest version of the file present in storage. When URL is hit with version query param, the file version specified in version query param is downloaded. The download will fail with 404 not found error if the specified version is no longer present in storage. If URL is hit without version query param, the latest file version present in storage is downloaded.
It is expected to provide API session i.e. vmware-api-session-id in header while using the URL to download the file. vmware-api-session-id can be obtained from POST /session operation Eg: wget --header="vmware-api-session-id: {sessionId}" fileDownloadEndpoint
This property was added in vSphere API 9.0.0.0.
missing or null
if the file is not present in storage i.e Content Library Item File Info.cached is False or library item is of VMTX Template type (as download of VMTX template is not supported currently)